Resource allocation for software development

ABSTRACT

Software development data indicative of a development activity is accessed. A component parameter of a component of a software development platform is set, in which the component parameter is based upon, at least in part, an anticipated component workload associated with the development actively. At least one system resource is allocated for the component of the software development platform based upon, at least in part, the component parameter.

BACKGROUND OF THE INVENTION

This disclosure relates to resource allocation in a software developmentenvironment.

Integrated software development platforms are in increasingly wide usein the software development industry. These often include developmentservices such as software configuration management systems, activitytracking systems, project management and tracking capabilities and soforth. These platforms are typically distributed over multiple systemsand provide comprehensive capabilities to make software developmentteams as efficient and effective as possible.

Such integrated software development platforms are often complex systemsthat typically include a variety of component configuration parametersthat can be adjusted by system administrators to tune the system foroptimal performance and reliability, e.g., network-related parametersfor distributed systems, capacity parameters for back-end serversystems, etc. System administrators typically learn how to tune theseparameters based on their own experience with the products and theparticular teams they are supporting. This level of tuning usually takesplace over some extended period of time and is therefore slow andinefficient, in addition to being dependent on the skill of theadministrator involved.

BRIEF SUMMARY OF THE INVENTION

In a first implementation, a method includes accessing, by a computingdevice, software development data indicative of a development activity.A component parameter of a component of a software development platformis set. The component parameter is based upon, at least in part, ananticipated component workload associated with the development activity.At least one system resource is allocated for the component of thesoftware development platform based upon, at least in part, thecomponent parameter.

One or more of the following features may be included. The softwaredevelopment data may include a software development schedule. Thesoftware development data may include a software development platformtransaction. Setting the component parameter may include setting anapplication server profile.

The at least one system resource may include one or more of a number ofCPU's, a number of CPU cores, memory, and disk space. The component ofthe software development platform may include a virtual machine. Atleast one system resource may be allocated for a second component of thesoftware development platform based upon, at least in part, allocatingthe at least one system resource for the component of the softwaredevelopment platform.

According to another implementation, a computer program product includesa computer readable medium having a plurality of instructions stored onit. When executed by a processor, the instructions cause the processorto perform operations including accessing software development dataindicative of a development activity. A component parameter of acomponent of a software development platform is set. The componentparameter is based upon, at least in part, an anticipated componentworkload associated with the development activity. At least one systemresource is allocated for the component of the software developmentplatform based upon, at least in part, the component parameter.

One or more of the following features may be included. The softwaredevelopment data may include a software development schedule. Thesoftware development data may include a software development platformtransaction. The instructions for setting the component parameter mayinclude instructions for setting an application server profile.

The at least one system resource may include one or more of a number ofCPU's, a number of CPU cores, memory, and disk space. The component ofthe software development platform may include a virtual machine.Instructions may be included for allocating at least one system resourcefor a second component of the software development platform based upon,at least in part, allocating the at least one system resource for thecomponent of the software development platform.

According to yet another implementation, a system includes a processorand a memory. A first software module is executable by the processor andthe memory. The first software module is configured to access softwaredevelopment data indicative of a development activity. A second softwaremodule is executable by the processor and the memory. The secondsoftware module is configured to set a component parameter of acomponent of a software development platform. The component parameterbased upon, at least in part, an anticipated component workloadassociated with the development activity. A third software module isalso executable by the processor and the memory. The third softwaremodule is configured to allocate at least one system resource for thecomponent of the software development platform based upon, at least inpart, the component parameter.

One or more of the following features may be included. The softwaredevelopment data may include a software development schedule. Thesoftware development data may include a software development platformtransaction. The second software module, configured to set the componentparameter, may be further configured to set an application serverprofile.

The at least one system resource may include one or more of a number ofCPU's, a number of CPU cores, memory, and disk space. The component ofthe software development platform may include a virtual machine. Afourth software module may be executable by the processor and thememory. The fourth software module may be configured to allocate atleast one system resource for a second component of the softwaredevelopment platform based upon, at least in part, allocating the atleast one system resource for the component of the software developmentplatform.

The details of one or more implementations are set forth in theaccompanying drawings and the description below. Other features willbecome apparent from the description, the drawings, and the claims.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

FIG. 1 diagrammatically depicts an allocation process coupled to ansoftware development platform.

FIG. 2 is a flowchart of a process executed by the allocation process ofFIG. 1.

DETAILED DESCRIPTION OF THE INVENTION

As will be appreciated by one skilled in the art, the present inventionmay be embodied as a method, system, or computer program product.Accordingly, the present invention may take the form of an entirelyhardware embodiment, an entirely software embodiment (includingfirmware, resident software, micro-code, etc.) or an embodimentcombining software and hardware aspects that may all generally bereferred to herein as a “circuit,” “module” or “system.” Furthermore,the present invention may take the form of a computer program product ona computer-usable storage medium having computer-usable program codeembodied in the medium.

Any suitable computer usable or computer readable medium may beutilized. The computer-usable or computer-readable medium may be, forexample but not limited to, an electronic, magnetic, optical,electromagnetic, infrared, or semiconductor system, apparatus, device,or propagation medium. More specific examples (a non-exhaustive list) ofthe computer-readable medium would include the following: an electricalconnection having one or more wires, a portable computer diskette, ahard disk, a random access memory (RAM), a read-only memory (ROM), anerasable programmable read-only memory (EPROM or Flash memory), anoptical fiber, a portable compact disc read-only memory (CD-ROM), anoptical storage device, a transmission media such as those supportingthe Internet or an intranet, or a magnetic storage device. Note that thecomputer-usable or computer-readable medium could even be paper oranother suitable medium upon which the program is printed, as theprogram can be electronically captured, via, for instance, opticalscanning of the paper or other medium, then compiled, interpreted, orotherwise processed in a suitable manner, if necessary, and then storedin a computer memory. In the context of this document, a computer-usableor computer-readable medium may be any medium that can contain, store,communicate, propagate, or transport the program for use by or inconnection with the instruction execution system, apparatus, or device.The computer-usable medium may include a propagated data signal with thecomputer-usable program code embodied therewith, either in baseband oras part of a carrier wave. The computer usable program code may betransmitted using any appropriate medium, including but not limited tothe Internet, wireline, optical fiber cable, RF, etc.

Computer program code for carrying out operations of the presentinvention may be written in an object oriented programming language suchas Java, Smalltalk, C++ or the like. However, the computer program codefor carrying out operations of the present invention may also be writtenin conventional procedural programming languages, such as the “C”programming language or similar programming languages. The program codemay execute entirely on the user's computer, partly on the user'scomputer, as a stand-alone software package, partly on the user'scomputer and partly on a remote computer or entirely on the remotecomputer or server. In the latter scenario, the remote computer may beconnected to the user's computer through a local area network (LAN) or awide area network (WAN), or the connection may be made to an externalcomputer (for example, through the Internet using an Internet ServiceProvider).

The present invention is described below with reference to flowchartillustrations and/or block diagrams of methods, apparatus (systems) andcomputer program products according to embodiments of the invention. Itwill be understood that each block of the flowchart illustrations and/orblock diagrams, and combinations of blocks in the flowchartillustrations and/or block diagrams, can be implemented by computerprogram instructions. These computer program instructions may beprovided to a processor of a general purpose computer, special purposecomputer, or other programmable data processing apparatus to produce amachine, such that the instructions, which execute via the processor ofthe computer or other programmable data processing apparatus, createmeans for implementing the functions/acts specified in the flowchartand/or block diagram block or blocks.

These computer program instructions may also be stored in acomputer-readable memory that can direct a computer or otherprogrammable data processing apparatus to function in a particularmanner, such that the instructions stored in the computer-readablememory produce an article of manufacture including instructions whichimplement the function/act specified in the flowchart and/or blockdiagram block or blocks.

The computer program instructions may also be loaded onto a computer orother programmable data processing apparatus to cause a series ofoperational steps to be performed on the computer or other programmableapparatus to produce a computer implemented process such that theinstructions which execute on the computer or other programmableapparatus provide steps for implementing the functions/acts specified inthe flowchart and/or block diagram block or blocks.

Referring to FIG. 1, there is shown allocation process 10 that mayreside on and may be executed by server computer 12, which may beconnected to network 14 (e.g., the Internet or a local area network).Examples of server computer 12 may include, but are not limited to: apersonal computer, a server computer, a series of server computers, amini computer, and a mainframe computer. Server computer 12 may be a webserver (or a series of servers) running a network operating system,examples of which may include but are not limited to: Microsoft®Windows® Server; Novell® Netware®; or Red Hat® Linux®, for example(Microsoft and Windows are registered trademarks of MicrosoftCorporation in the United States, other countries, or both; Novell andNetWare are registered trademarks of Novell Corporation in the UnitedStates, other countries, or both; Red Hat is a registered trademark ofRed Hat Corporation in the United States, other countries, or both; andLinux is a registered trademark of Linus Torvalds in the United States,other countries, or both).

As will be discussed below in greater detail, allocation process 10 mayaccess software development data indicative of a development activity.Allocation process 10 may further set a component parameter of acomponent of a software development platform. The component parametermay be based upon, at least in part, an anticipated component workloadassociated with the development activity. At least one system resourcemay be allocated for the component of the software development platformbased upon, at least in part, the component parameter.

The instruction sets and subroutines of allocation process 10, which maybe configured as one or more software modules, and which may be storedon storage device 16 coupled to server computer 12, may be executed byone or more processors (not shown) and one or more memory modules (notshown) incorporated into server computer 12. Storage device 16 mayinclude but is not limited to: a hard disk drive; a solid state drive; atape drive; an optical drive; a RAID array; a random access memory(RAM); and a read-only memory (ROM).

Server computer 12 may be network accessible via network 14, examples ofwhich may include, but are not limited to, a local area network, a widearea network, an intranet, the Internet, etc. Network 14 may beconnected to one or more secondary networks (e.g., network 18), examplesof which may include but are not limited to: a local area network; awide area network; or an intranet, for example.

Server computer 12 may execute software development platform 20, anexample of software development platform 20 may include, but is notlimited to, Rational Team Concert™ by IBM. (Rational Team Concert is atrademark of IBM Corporation in the United States, other countries, orboth). Software development platform 20 may provide various softwaredevelopment tools including, but not limited to, planning tools, sourcecode editing and management tools (e.g., software configurationmanagement tools), and automated testing tools. Examples of such toolsmay include Rational® Quality Manager, Rational® Requirements Composer,Rational Project Conductor™, (all by IBM), etc., which may includecomponents of the software development platform and/or may bestand-alone applications which may, in some embodiments, interact withthe software development platform. (Rational is a registered trademarkof IBM Corporation in the United States, other countries, or both;Rational Project Conductor is a trademark of IBM Corporation in theUnited States, other countries, or both). Software development platform20 may be accessed by one or more client applications (e.g., clientapplications 22, 24, 26, 28, examples of which may include but are notlimited to web browsers (e.g., Microsoft Internet Explorer®, Apple®Safari®, etc.) or a custom interface application. (Internet Explorer isa registered trademark of Microsoft Corporation in the United States,other countries, or both, and Apple and Safari are registered trademarksof Apple Inc. in the United States, other countries, or both).

The instruction sets and subroutines of software development platform 20(and of any tools and/or modules incorporated into software developmentplatform 20, and/or interacting with software development platform 20),which may be configured as one or more software modules, and which maybe stored on storage device 16 coupled to server computer 12 may beexecuted by one or more processors (not shown) and one or more memorymodules (not shown) incorporated into server computer 12. Additionally,software development platform 20 (and any tools and/or modulesincorporated into software development platform 20, and/or interactingwith software development platform 20) may be distributed over multiplesystems and/or server computers.

The instruction sets and subroutines of client applications 22, 24, 26,28, which may be configured as one or more software modules, and whichmay be stored on storage devices 30, 32, 34, 36 (respectively) coupledto client electronic devices 38, 40, 42, 44 (respectively), may beexecuted by one or more processors (not shown) and one or more memorymodules (not shown) incorporated into client electronic devices 38, 40,42, 44 (respectively). Storage devices 30, 32, 34, 36 may include butare not limited to: hard disk drives; solid state drives; tape drives;optical drives; RAID arrays; random access memories (RAM); read-onlymemories (ROM), compact flash (CF) storage devices, secure digital (SD)storage devices, and memory stick storage devices. Examples of computingdevices 38, 40, 42, 44 may include, but are not limited to, personalcomputers 38, 42, laptop computer 40, 44, for example. Of course variousother client electronic devices may equally be utilized. Using clientapplications 22, 24, 26, 28, users 46, 48, 50, 52 may, for example,perform various software development activities, including developmentplanning, collaboration with other users, code editing, softwaretesting, etc.

Users 46, 48, 50, 52 may access software development platform 20directly through the device on which the client application (e.g.,client applications 22, 24, 26, 28) is executed, namely clientelectronic devices 38, 40, 42, 44, for example. Users 46, 48, 50, 52 mayaccess software development platform 20 directly through network 14 orthrough secondary network 18. Further, server computer 12 (i.e., thecomputer that executes software development platform 20 and/orallocation process 10) may be connected to network 14 through secondarynetwork 18, as illustrated with phantom link line 54.

The various client electronic devices may be directly or indirectlycoupled to network 14 (or network 18). For example, personal computers38, 42 are shown directly coupled to network 14 via a hardwired networkconnection. Further, notebook computer 44 is shown directly coupled tonetwork 18 via a hardwired network connection. Laptop computer 40 isshown wirelessly coupled to network 14 via wireless communicationchannel 56 established between laptop computer 40 and wireless accesspoint (i.e., WAP) 58, which is shown directly coupled to network 14. WAP58 may be, for example, an IEEE 802.11a, 802.11b, 802.11g, Wi-Fi, and/orBluetooth device that is capable of establishing wireless communicationchannel 56 between laptop computer 40 and WAP 58.

As is known in the art, all of the IEEE 802.11x specifications may useEthernet protocol and carrier sense multiple access with collisionavoidance (i.e., CSMA/CA) for path sharing. The various 802.11xspecifications may use phase-shift keying (i.e., PSK) modulation orcomplementary code keying (i.e., CCK) modulation, for example. As isknown in the art, Bluetooth is a telecommunications industryspecification that allows e.g., mobile phones, computers, and personaldigital assistants to be interconnected using a short-range wirelessconnection.

Client electronic devices 38, 40, 42, 44 may each execute an operatingsystem, examples of which may include but are not limited to Microsoft®Windows®, Microsoft Windows CE®, Red Hat® Linux®, or a custom operatingsystem (Windows CE is a registered trademark of Microsoft Corporation inthe United States, other countries, or both).

Referring also to FIG. 2, allocation process 10 may access 100 softwaredevelopment data indicative of a development activity. A componentparameter of a component of a software development platform may be set102. The component parameter may be based upon, at least in part, ananticipated component workload associated with the development activity.Allocation process 10 may also allocate 104 at least one system resourcefor the component of the software development platform based upon, atleast in part, the component parameter. As such, in an embodiment,allocation process 10 may allocate 104 at least one system resource fora component of a software development platform for an anticipatedcomponent workload.

As discussed above, server computer 12 may execute a softwaredevelopment platform (e.g., software development platform 20). Softwaredevelopment platform 20 may provide access to various development tools(e.g., various components of the software development platform), eitheras modules of software development platform 20 or as stand-aloneapplications which can be accessed through, managed by, and/or utilizedin conjunction with software development platform. Further, as describedabove, the various components of software development platform 20 may beexecuted on a single server computer (e.g., server computer 12).Additionally/alternatively, the various components may be distributedover multiple server computers or multiple computing systems.

Generally, software development may include phases, such as a planningphase, a coding/development phase, and a testing phase. Of coursevarious additional/alternative phases may be included, which may varydepending upon the project. For example, during the planning there maybe a relatively high degree of interaction between the various usersmaking up the development team as each user gains an understanding ofthe specific development tasks that he has been assigned. During thisplanning phase, collaboration components (such as Rational Team ConcertWorkItem by IBM Corporation) of the software development platform may behighly utilized. Similarly, during the coding/development phase, varioususers of the software development team may utilize softwareconfiguration management components of the software developmentplatform, e.g., as they perform check-outs and deliveries of changedsource code. Further, during the testing phase automated testingcomponents of the software development platform may be highly utilizedfor testing the developed code. The phases, activities, and softwaredevelopment platform components described above should be understood asillustrative, and not a limitation on the present disclosure, as thephases, activities, and components may vary depending upon nature of thesoftware development project, design criteria, and user need.

While generally, software development may include various phases, thephases, and the activities within the phases may overlap. Utilizingsoftware development platform 20 various users working on a softwaredevelopment project may, for example, be able to view and edit sourcecode, review defect repots, check-in edited source code, initiatebuilds, and run automated tests from the same environment, and even incommon time frames. As such, some, or all, of the various components ofsoftware development platform 20 may all be utilized throughout thesoftware development project. However, the workloads experienced by thevarious components may vary throughout the project with differentcomponents experiencing different workloads during different phasesand/or different activities of the software development project.

As mentioned, allocation process 10 may access 100 software developmentdata indicative of a development activity. As also noted above, softwaredevelopment may include many development activities. While the variousactivities (and components of software development platform 20 utilizedin carrying out the various activities) may be performed to some degreethroughout the software development project, specific activities may begenerally grouped (e.g., in terms of greatest occurrence and/orexperienced component workload) according to the various phases of thesoftware development project.

The software development data accessed 100 by allocation process 10 mayinclude a software development schedule. Such a software developmentschedule (e.g., software development schedule 60, which may reside as adocument, timeline, workflow table, etc., that may be stored on astorage device, such as storage device 16 coupled to server computer 12)may explicitly state timelines and/or checkpoints associated withdifferent phases of the software development project. Allocation process10 may access 100 software development schedule 60, including dataindicative of various development activities that may occur at differentgeneral times. For example, software development schedule 60 mayindicate that system testing of the software being developed is to occurduring the general time frame of November 20 through November 22.

While software development schedule 60 may include at least a generaltimeline of the software development project and the activities that mayoccur at various general times, the timing of the phases and activitiesmay change throughout the course of the software development project. Insome instances, software development schedule 60 may be regularlyupdated to reflect such changes. In such a situation, accessing 100software development schedule 60 may continue to provide softwaredevelopment data indicative of a development activity occurring at agiven general time. For example, the software development project mayexperience delays during coding/development. Software developmentschedule 60 may be updated to indicate that system testing of thesoftware being developed may occur in the general timeframe of November21 through November 23.

In an embodiment, the software development data may include a softwaredevelopment platform transaction. Software development platformtransactions may include instances of use of the various components ofsoftware development platform 20. For example, a software developmentplatform transaction may include a functional test run on a piece ofcode. Similarly, another software development platform transaction mayinclude a 500 user system test of the completed software product.Software development data indicative of a development activity mayinclude such software development platform transactions. Allocationprocess 10 may access 100 transaction data (e.g., which may be reside intransaction log 62 stored on storage device 16 coupled to servercomputer 12). Phases of the software development project may be inferredbased upon, at least in part, the relative frequency and nature of thevarious software development platform transactions accessed 100 via thetransaction data.

Allocation process 10 may set a component parameter of a component ofsoftware development platform 20. The component parameter may be basedupon, at least in part, an anticipated component workload associatedwith the development activity. For example, during a developmentactivity included within the coding/development phase of the softwaredevelopment project some testing, such as functional testing of a pieceof code, is likely to occur. However, such a development activity may beanticipated to place a relatively small workload on an automated testingcomponent of software development platform 20. During a testing phase ofthe software development project, system verification testing may becarried out representing a relatively large number of users in severaloperating system environments. Such system verification testing may havelarge anticipated workload associated with the automated testingcomponent.

A component parameter of the component of software development platform20 may include, for example, various system resources that may allow forsatisfactory performance of the component under the anticipatedworkload. Further, the component parameter may relate to a timeframeassociated with the development activity, during which the varioussystem resources are desired to accommodate the anticipated workload.Accordingly, the component parameter(s) may include system resourceparameters and timing parameters.

Setting 102 the component parameter may include setting 106 anapplication server profile. A server profile may include one or morecomponent parameters based upon, at least in part, an anticipatedcomponent workload associated with the development activity. Forexample, various server profiles may be provided for each componentassociated with different timeframes during the software developmentproject based upon, at least in part, different anticipated workloadsassociated with the various components during the different timeframes.Continuing with the above-stated example in which individual users mayrun functional tests of pieces of code during the coding/developmentphase of the software development project, the anticipated workloadassociated with the testing component of software development platformduring the coding/development phase may be relatively low. A serverprofile associated with the testing component during thecoding/development phase may include one or more component parametersthat may reflect the relatively low anticipated testing componentworkload. Similarly, a relatively high workload associated with thetesting component may be anticipated during the testing phase of thesoftware development project. A server profile associated with thetesting component during the testing phase may include one or morecomponent parameters that may reflect the relatively high anticipatedworkload. A server profile may be associated with each component foreach phase of the software development project.Additionally/alternatively, a server profile may be associated with eachphase of the software development project. In such an embodiment, eachserver profile may include parameter settings for each component. Theparameter setting for each component may be based upon, at least inpart, an anticipated workload associated with each component for thesoftware development phase of the server profile. Variousadditional/alternative server profiles may similarly be implemented.

Allocation process 10 may allocate 104 at least one system resource forthe component of the software development platform based upon, at leastin part, the component parameter. As noted above, the componentparameter may include system resource parameters, e.g., which mayinclude system parameter type as well as a quantity of the systemresource. Additionally, the component parameter may include a timingcomponent that may be based upon, at least in part, an anticipatedcomponent workload associated with the component at least a generalgiven time. As such, allocation process 10 may allocate 104 one or moresystem resources at a specified time to allow for satisfactoryperformance of the component under the anticipated workload at theanticipated time.

Again referring to the above-mentioned example in which individual usersmay run some functional testing on pieces of code during thecoding/development phase of the software development project (i.e.,producing a relatively low anticipated component workload associatedwith a testing component of software development platform 20), whilelarge scale system verification testing may take place during a testingphase of the software development project (i.e., producing a relativelyhigh anticipated component workload associated with the testingcomponent of software development platform 20). Allocation process 10may allocate at least one system resource for the testing component toprovide satisfactory performance under the low anticipated workload forthe testing component during the coding/development phase. As thesoftware development project moves into the testing phase (e.g., as maybe indicated by the accessed 100 software development data), allocationprocess 10 may allocate 104 at least one system resource for the testingcomponent to provide satisfactory performance under the high anticipatedworkload for the testing component during the testing phase of thesoftware development project. The timing of allocating 104 the at leastone system resource may be based upon, at least in part, the accessed100 software development data and the set 102 component parameter, asdiscussed above.

The at least one system resource may include one or more of a number ofCPU's, a number of CPU cores, memory, and disk space. Also, thecomponent of the software development system may include a virtualmachine. Accordingly, allocation process 10 may, for example, allocate104 a given number of CPU's and a given number of CPU cores, as well asa given volume of memory and disk space (one or more of which may bebased upon, at least in part the component parameter) to a componentvirtual machine.

Allocation process 10 may allocate 108 at least one system resource fora second component of the software development platform based upon, atleast in part, allocating 104 the at least one system resource for thecomponent of the software development platform. For example, asgenerally discussed above, the anticipated workload for variouscomponents of software development platform 20 may vary throughout thesoftware development project. In such a manner, a relatively highanticipated workload associated with one component may generally beassociated with a relatively low anticipated workload associated with asecond component during the same general timeframe. For example, duringthe planning phase, a relatively high workload associated with acollaboration component may be anticipated. Allocation process 10 mayallocate 104 at least one system resource to the collaboration componentto allow satisfactory performance of the collaboration components underthe anticipated relatively high workload. Similarly, during the planningphase a relatively low workload associated with a testing component maybe anticipated. As such, allocation process 10 may allocate 108 at leastone system resource for the testing component of the softwaredevelopment platform indicative of a relatively low anticipated testingcomponent workload based upon the allocation 104 of resources based upona relatively high anticipated workload for the collaboration components.

Allocation process 10 may, effectively, anticipate a workload associatedwith each component of software development platform 20 at any giventime during the software development project. Allocation process 10 may,accordingly, allocate 104 one or more system resources to the variouscomponents of software development platform 20 to allow for satisfactoryperformance of the various components, given their anticipatedassociated workloads, at any given time during the software developmentproject. Accordingly, the at least one system resource may be allocated104 in advance of, at in time to satisfy, a given anticipated workloadof a component of software development platform.

The flowchart and block diagrams in the Figures illustrate thearchitecture, functionality, and operation of possible implementationsof systems, methods and computer program products according to variousembodiments of the present invention. In this regard, each block in theflowchart or block diagrams may represent a module, segment, or portionof code, which comprises one or more executable instructions forimplementing the specified logical function(s). It should also be notedthat, in some alternative implementations, the functions noted in theblock may occur out of the order noted in the figures. For example, twoblocks shown in succession may, in fact, be executed substantiallyconcurrently, or the blocks may sometimes be executed in the reverseorder, depending upon the functionality involved. It will also be notedthat each block of the block diagrams and/or flowchart illustration, andcombinations of blocks in the block diagrams and/or flowchartillustration, can be implemented by special purpose hardware-basedsystems that perform the specified functions or acts, or combinations ofspecial purpose hardware and computer instructions.

The terminology used herein is for the purpose of describing particularembodiments only and is not intended to be limiting of the invention. Asused herein, the singular forms “a”, “an” and “the” are intended toinclude the plural forms as well, unless the context clearly indicatesotherwise. It will be further understood that the terms “comprises”and/or “comprising,” when used in this specification, specify thepresence of stated features, integers, steps, operations, elements,and/or components, but do not preclude the presence or addition of oneor more other features, integers, steps, operations, elements,components, and/or groups thereof.

The corresponding structures, materials, acts, and equivalents of allmeans or step plus function elements in the claims below are intended toinclude any structure, material, or act for performing the function incombination with other claimed elements as specifically claimed. Thedescription of the present invention has been presented for purposes ofillustration and description, but is not intended to be exhaustive orlimited to the invention in the form disclosed. Many modifications andvariations will be apparent to those of ordinary skill in the artwithout departing from the scope and spirit of the invention. Theembodiment was chosen and described in order to best explain theprinciples of the invention and the practical application, and to enableothers of ordinary skill in the art to understand the invention forvarious embodiments with various modifications as are suited to theparticular use contemplated.

Having thus described the invention of the present application in detailand by reference to embodiments thereof, it will be apparent thatmodifications and variations are possible without departing from thescope of the invention defined in the appended claims.

1-7. (canceled)
 8. A computer program product comprising a computerreadable medium having a plurality of instructions stored thereon,which, when executed by a processor, cause the processor to performoperations comprising: accessing software development data indicative ofa development activity; setting a component parameter of a component ofa software development platform, the component parameter based upon, atleast in part, an anticipated component workload associated with thedevelopment activity; and allocating at least one system resource forthe component of the software development platform based upon, at leastin part, the component parameter.
 9. The computer program product ofclaim 8, wherein the software development data includes a softwaredevelopment schedule.
 10. The computer program product of claim 8,wherein the software development data includes a software developmentplatform transaction.
 11. The computer program product of claim 8,wherein the instructions for setting the component parameter includeinstructions for setting an application server profile.
 12. The computerprogram product of claim 8, wherein the at least one system resourceincludes one or more of a number of CPU's, a number of CPU cores,memory, and disk space.
 13. The computer program product of claim 8,wherein the component of the software development platform includes avirtual machine.
 14. The computer program product of claim 8, furthercomprising instructions for allocating at least one system resource fora second component of the software development platform based upon, atleast in part, allocating the at least one system resource for thecomponent of the software development platform.
 15. A system comprising:a processor; a memory; a first software module executable by theprocessor and the memory, the first software module configured to accesssoftware development data indicative of a development activity; a secondsoftware module executable by the processor and the memory, the secondsoftware module configured to set a component parameter of a componentof a software development platform, the component parameter based upon,at least in part, an anticipated component workload associated with thedevelopment activity; and a third software module executable by theprocessor and the memory, the third software module configured toallocate at least one system resource for the component of the softwaredevelopment platform based upon, at least in part, the componentparameter.
 16. The system of claim 15, wherein the software developmentdata includes a software development schedule.
 17. The system of claim15, wherein the software development data includes a softwaredevelopment platform transaction.
 18. The system of claim 15, whereinthe second software module, configured to set the component parameter,is further configured to set an application server profile.
 19. Thesystem of claim 15, wherein the at least one system resource includesone or more of a number of CPU's, a number of CPU cores, memory, anddisk space.
 20. The system of claim 15, wherein the component of thesoftware development platform includes a virtual machine.
 21. The systemof claim 15, further comprising a fourth software module executable bythe processor and the memory, the fourth software module configured toallocate at least one system resource for a second component of thesoftware development platform based upon, at least in part, allocatingthe at least one system resource for the component of the softwaredevelopment platform.